Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat/3879/map order #3905

Merged
merged 12 commits into from
Feb 3, 2025
Merged

Feat/3879/map order #3905

merged 12 commits into from
Feb 3, 2025

Conversation

BenediktMehl
Copy link
Collaborator

@BenediktMehl BenediktMehl commented Jan 31, 2025

Order maps

Closes: #3879

Description

Maps should always be in the same ascending order by: fileName + fileChecksum

Definition of Done

A PR is only ready for merge once all the following acceptance criteria are fulfilled:

  • Changes have been manually tested
  • All TODOs related to this PR have been closed
  • There are automated tests for newly written code and bug fixes
  • All bugs discovered while working on this PR have been submitted as issues (if not already an open issue)
  • Documentation (GH-pages, analysis/visualization READMEs, parser READMEs, --help, etc.) has been updated (almost always necessary except for bug fixes)
  • CHANGELOG.md has been updated

Screenshots or gifs

Copy link

sonarqubecloud bot commented Feb 3, 2025

Copy link

sonarqubecloud bot commented Feb 3, 2025

@BenediktMehl BenediktMehl merged commit 95051ad into main Feb 3, 2025
8 checks passed
@BenediktMehl BenediktMehl deleted the feat/3879/map-order branch February 3, 2025 10:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Multiple maps should always be rendered in the same order
2 participants